Update a file protection replication session
Network-attached storage is a file-level storage architecture that makes stored data more accessible to networked devices.
About this task
See Understanding PowerMax File for storage systems for an overview of PowerMax File.
The Update operation reconstructs missing file systems on the destination NAS Server. During the lifetime of a replication session, it is possible that file systems and clone may be added to the source NAS server. When this situation happens, the replication session is supposed to automatically add file systems and clone to the destination NAS server. It is possible, for some unspecified reason, that this may not happen. In this case, the replication session is considered inconsistent. The NAS server replication update action is designed to rectify this inconsistency. When the replication session update action is issued, the file systems that are associated with the source NAS server are enumerated. If there is no file system with the same name on the destination NAS server, then it is created, and replication is established between them. Similarly, if there is a file system with the same name on both NAS servers but there is no replication established, then it is created. When there are missing file systems or the file systems are not replicated, an alert SOME_FS_REP_SESSIONS_NOT_CREATED is generated.
 | NOTE: Adding a file system to a NAS server under
replication would create the corresponding file system on the destination.Cloning a
replicated file system would follow the same workflow as the above point. Completing
the baseline copy would take some time depending on the data on the source side and
the session status is SyncInProg but eventually transitions to synchronized
(synchronous replication) or consistent state (asynchronous replication). Deleting a
file system under replication from the source does not delete the corresponding file
system on the destination. |